Information handling system totem tracking management

ABSTRACT

An information handling system touchscreen display interacts with totem devices by recognizing and tracking spectral signatures of the totem devices so that totem positions are reported as a single length, width and rotational orientation message to a host operating system. Ignore zones and hysteresis time periods are defined from the position message based upon totem context so that the host operating system processes touchscreen inputs with minimal latency and improved accuracy. Communication and battery charging are provided to the totem by the touchscreen display will illumination directed to the totem position.

CROSS REFERENCE TO RELATED APPLICATIONS

U.S. patent application Ser. No. 15/347,251, entitled “InformationHandling System Capacitive Touch Totem Management” by inventors Jace W.Files, Larry A. Stone, Mark S. Sears, Yagiz C. Yildiz, and Sujata Das,filed on same day herewith, describes exemplary methods and systems andis incorporated by reference in its entirety.

U.S. patent application Ser. No. 15/347,304, entitled “InformationHandling System Variable Capacitance Totem Input Management” byinventors Larry A. Stone, Jace W. Files, and Yagiz C. Yildiz, filed onsame day herewith, describes exemplary methods and systems and isincorporated by reference in its entirety.

U.S. patent application Ser. No. 15/347,337, entitled “InformationHandling System Capacitive Touch Totem with Optical CommunicationSupport” by inventors Jace W. Files and Yung-Chun Liu, filed on same dayherewith, describes exemplary methods and systems and is incorporated byreference in its entirety.

U.S. patent application Ser. No. 15/347,361 entitled “InformationHandling System Capacitive Touch Totem with Optical CommunicationSupport” by inventors Larry A. Stone, Jace W. Files, Yagiz C. Yildiz,and Mark S. Sears, filed on same day herewith, describes exemplarymethods and systems and is incorporated by reference in its entirety.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention relates in general to the field of informationhandling system user interface management, and more particularly, to aninformation handling system capacitive touch totem management.

Description of the Related Art

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option available to users is information handling systems. Aninformation handling system generally processes, compiles, stores,and/or communicates information or data for business, personal, or otherpurposes thereby allowing users to take advantage of the value of theinformation. Because technology and information handling needs andrequirements vary between different users or applications, informationhandling systems may also vary regarding what information is handled,how the information is handled, how much information is processed,stored, or communicated, and how quickly and efficiently the informationmay be processed, stored, or communicated. The variations in informationhandling systems allow for information handling systems to be general orconfigured for a specific user or specific use such as financialtransaction processing, airline reservations, enterprise data storage,or global communications. In addition, information handling systems mayinclude a variety of hardware and software components that may beconfigured to process, store, and communicate information and mayinclude one or more computer systems, data storage systems, andnetworking systems.

Information handling systems interact with end users through a varietyof input and output devices. Typical input devices include keyboards,mice, touchpads, etc. that accept input actions and convert the inputactions into signals interpreted by a processor. Typically output ispresented at a display device, such as a flat panel LCD or OLED displaypanel. Flat panel displays provide high quality display resolution in athin form factor. Some examples of flat panel displays include liquidcrystal displays (LCD) that alter a presented back light to generateimages, and organic light-emitting displays (OLED) that generate imageswith pixels that create desired light values. One advantage of flatpanel displays is that portable information handling systems canintegrate the displays into a portable housing while supporting a thinform factor and reduced power consumption. Another advantage is thatflat panel displays readily adapt to include touchscreen inputs. Endusers often prefer to interact with user interfaces by performing touchinputs at a display touchscreen so that keyboard and mouse devices arenot needed.

As touchscreen displays have improved and been adopted by end users inportable information handling systems, touch interfaces have become morecommon and intuitive. Further, touchscreen protective surfaces havebecome tougher and more resistant to breakage and scratching. As aresult, desktop touchscreen displays that are horizontally disposed havebecome accepted as a flexible user interface. A horizontally-disposedtouchscreen display rests on a desktop surface and presents userinterfaces that end users touch to perform inputs. For example, adisplayed keyboard allows an end user to make keyed inputs instead ofrelying on a fixed keyboard. With appropriately designed userinterfaces, a horizontally-disposed touchscreen provides an interfacethat works more efficiently than mouse-based interfaces since an enduser simply touches the input on the display resting on a desktop infront of the user.

One difficulty with the use of a horizontally-disposed display is thatthe touchscreen will often receive inadvertent touches that are notintended as inputs to the information handling system. For example, apalm or object resting on a touchscreen may be placed for userconvenience or comfort rather than to generate an input by a touch.Typically touchscreen displays filter touches to identify finger touchesas intended touches and to avoid inadvertent touches as inputs. In adesktop environment where a touchscreen display ishorizontally-disposed, such filtering may consume processing resourcesso that latency is introduced between when an end user makes an intendedtouch and the intended touch is recorded on the display as an input. Onthe other hand, even where adequate processing resources are availableto filter touch inputs in a timely manner, rapid processing of touchescan result in presentation of inputs where no input was in factintended. Although post-processing can remove such unintendedpresentations, even temporary presentation of incorrect data can lead toend user confusion and a poor user experience.

With horizontal disposition of touchscreen displays, totems have becomean option to aid end user interactions with user interfaces. A totem isa device, often without any integrated intelligence, that interacts bytouches to the display surface. For example, a mouse totem might move acursor on a display based upon the position of the mouse totem on ahorizontally disposed touchscreen display. Totem devices offer physicalmanipulation that translates into touch inputs to improve interfaceintuitiveness and usability. However, a totem tends to touch across awider area than a finger touch, which tends to introduce difficulty foran operating system to recognize the totem versus inadvertent bulktouches, such as may be introduced by a palm. Further, as an end usermanipulates a totem the totem bottom surface tends to lift from thetouchscreen in an uneven manner that may lead to improper totemrecognition and tracking. As totem contact regions lift off andre-contact a touchscreen display, irregular and unpredictable touchinputs increase demands on processing resources, often resulting inlatency for totem input and incorrect tracking of the inputs at thetouchscreen.

In some instances, totem devices include some level of intelligence thataids in the management of inputs. For example, a totem may include aBluetooth transmitter, a microprocessor, an accelerometer and externallighting that aids end user interaction. One difficulty that arises withintelligent totems is tracking multiple totem devices so that a deviceassociated with an intelligent input or interaction is at a location onthe touchscreen display that is associated with the input. Aregistration process that associates a particular totem with a touchlocation introduces complexity that an end user must deal with as inputsare made, totems are added or removed and user interfaces change. Inaddition, registration of totems tends to increase latency and slowinteractions by having wireless coordination completed before an enduser can interact with a totem. Further, intelligent totems typicallyrequire some internal power source, such as a battery, so that keepingthe battery charged or fresh presents the end user with an additionalcomplexity that detracts from the simple nature of totems as “dumb”input devices.

SUMMARY OF THE INVENTION

Therefore, a need has arisen for a system and method which provides aninformation handling system totem user interaction with efficient andaccurate totem tracking having minimal latency.

A further need exists for a system and method which provide reducedfalse touch detection by enhancing totem touch detection when a totem isin active use.

A further need exists for a system and method which provide time basedmonitoring of totem interactions with a variably set hysteresis based onuser interface context to quickly and accurately measure totem inputs.

A further need exists for a system and method which providecommunication between a totem and touchscreen display using illuminationpresented at the display and sensed by the totem.

A further need exists for a system and method which provide localcontrol at a touchscreen display with a totem in the absence of a hostoperating system interface.

In accordance with the present invention, a system and method areprovided which substantially reduce the disadvantages and problemsassociated with previous methods and systems for interacting a totem andan information handling system through a horizontally disposedtouchscreen display. Totem recognition and tracking, such as by adedicated digital signal processor using spectral analysis, resolvestotem position to a length, width and rotational orientation on thetouchscreen display to reduce host operating system processing andlatency related to complex touch context. Ignore zones and hysteresisadapt for a totem based upon user interface context to focus touchprocessing on appropriate areas without introducing extraneousprocessing tasks or false input detection. Direct communication betweena display and totem with light illumination at the totem lower surfaceenables command communication for a totem without a wireless interfaceor host operating system support. Two way communication is supported byselectively interfacing capacitance with contact points of the totem,such as when weight is placed on the totem indicating an end user input.

More specifically, an information handling system processes informationwith processing components, such as a CPU, memory, embedded controllersand firmware instructions. The information handling system acceptsinputs made as touches to a touchscreen display, such as in a horizontalconfiguration resting on a desktop. Totem devices rest on thetouchscreen display to accept end user manipulation and translate theend user manipulation into physical inputs detected as touches at thetouchscreen display. A totem analyzer, such as a digital signalprocessor, performs totem recognition by searching for totem signatureson the touchscreen display, such as with spectral analysis of detectedtouch capacitance in a frequency, amplitude or phase domain. The totemanalyzer reports totem positions to a host operating system as a singletouch location message, such as a length, width and rotationalorientation message. In response, a touch controller or operating systemenforces ignore zones proximate to the totem and hysteresis forprocessing inputs related to touches proximate the totem so thatprocessing resources are not diverted to manage detected inputs wherethe inputs likely relate to inadvertent touches related to toteminteractions. Ignore zones and hysteresis adapt based upon detectedcontext at the touchscreen display, such as the relative location of thetotem at the display, the user interface associated with the totem, theend user hand location and the number of totems in use at thetouchscreen display. Focusing touch detection to respond more quickly toexpected touches of an intended nature while ignoring likely unintendedtouches provides a more efficient totem identification, registration andtracking.

In one embodiment, communication is supported between a logic device ofthe totem, such as a microcontroller, and a display logic device or hostoperating system. For example, a light detector disposed on the bottomsurface of the totem detects illumination of the touchscreen display toreceive commands. As another example, manipulation of a capacitivesource interfacing with a totem contact point provides inputs to thetouchscreen display in the form of varying capacitive input. By managingsome or all totem interactions with a scalar of the touchscreen display,commands for local functions are enabled, such as charging of the totembattery with illumination provided from the display to the totem bottomsurface or associating particular totems with touches made at thetouchscreen display.

The present invention provides a number of important technicaladvantages. One example of an important technical advantage is thattotem interactions between an information handling system andtouchscreen display have improved latency and accuracy through spectralanalysis of the totem signature that resolves totem position to a singlemessage for the host operating system. Tracking one or more totems witha dedicated signal processor reduces processing demands placed on thehost operating system and allows accurate definition of ignore zones andhysteresis related to the totem based upon user interface context. Insome use cases, host operating system interaction is avoided by directlyinterfacing a touchscreen display scalar to command the totem, such aswith illumination of commands to a light detector of the totem bottomsurface. In such an embodiment, totem battery charge is maintained witha scalar by directing illumination at the totem bottom surface as thetotem indicates battery charge as low. Active management at atouchscreen display physical layer, such as with a touch controller,scalar or other embedded controllers reduces latency and improvesusability and user experience.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerousobjects, features and advantages made apparent to those skilled in theart by referencing the accompanying drawings. The use of the samereference number throughout the several figures designates a like orsimilar element.

FIG. 1 depicts an information handling system interfaced with ahorizontally-disposed touchscreen display having totems disposed on thetouchscreen surface:

FIG. 2 depicts a block diagram of a system for interfacing totems on atouchscreen display with a host information handling system;

FIG. 3 depicts a flow diagram of a process for defining host informationhandling system interactions with totems disposed on a touchscreendisplay;

FIG. 4 depicts an example embodiment of a system for trackinginteraction settings of totems disposed on a touchscreen display:

FIG. 5 depicts a flow diagram of process for adapting totem inputresponsiveness based upon totem usage states;

FIG. 6 depicts a flow diagram of a process for adjusting totemresponsiveness based upon totem motion;

FIG. 7 depicts a side cutaway view of a totem having touch contactpoints with variable capacitance and having interactions with lightoutput at the display;

FIG. 8 depicts a state diagram of totem settings based upon detectedweight placed upon the totem:

FIG. 9 depicts a block diagram of totem interactions managed locally ata touchscreen display scalar:

FIG. 10 depicts a touchscreen display having illumination zones managedto interact with a totem:

FIG. 11 depicts a flow diagram of a process for communicating with atotem using illumination at the totem bottom surface;

FIG. 12 depicts a flow diagram of a process for coordinating charge of atotem battery with touchscreen display illumination

FIG. 13 depicts a block diagram of a system for detecting a totemspectral signature;

FIG. 14 depicts an example embodiment of a totem position resolved fromspectral analysis;

FIG. 15 depicts an example embodiment of a totem position resolved fromspectral analysis of multiple totem touch regions; and

FIG. 16 depicts an example embodiment of a totem position resolved fromspectral analysis of a circular totem touch region.

DETAILED DESCRIPTION

Totem devices resting on a horizontally-disposed touchscreen displayinteract with an information handling system by adapting touchscreendisplay operations for detecting touches and presenting visualinformation. For purposes of this disclosure, an information handlingsystem may include any instrumentality or aggregate of instrumentalitiesoperable to compute, classify, process, transmit, receive, retrieve,originate, switch, store, display, manifest, detect, record, reproduce,handle, or utilize any form of information, intelligence, or data forbusiness, scientific, control, or other purposes. For example, aninformation handling system may be a personal computer, a networkstorage device, or any other suitable device and may vary in size,shape, performance, functionality, and price. The information handlingsystem may include random access memory (RAM), one or more processingresources such as a central processing unit (CPU) or hardware orsoftware control logic, ROM, and/or other types of nonvolatile memory.Additional components of the information handling system may include oneor more disk drives, one or more network ports for communicating withexternal devices as well as various input and output (L/O) devices, suchas a keyboard, a mouse, and a video display. The information handlingsystem may also include one or more buses operable to transmitcommunications between the various hardware components.

Referring now to FIG. 1, an information handling system 10 interfaceswith a horizontally-disposed touchscreen display 34 having totems 40disposed on the touchscreen surface. Information handling system 10 ofthe example embodiment has a portable main housing 12 that containsprocessing components for processing information and a lid portion 14rotationally-coupled to the main housing 12. A cover portion 16 fitsover the processing components to provide an upper support surface. Inthe example embodiment, the processing components include a centralprocessing unit (CPU) 18, random access memory (RAM) 20, a chipset 22,an embedded controller 24 and a wireless network interface card (WNIC)26. During normal operations, CPU 18 executes an operating system thatmanages interaction with processing components and supports execution ofapplications stored in RAM 20. Chipset 22 includes a variety ofcontrollers, processors and flash memory to manage operation ofprocessing components on a physical layer. Embedded controller 24, suchas a keyboard controller, includes power management logic and acceptsinputs from input devices, such as a keyboard, mouse, touchpad ortouchscreen. WNIC 26 includes wireless networking devices thatcommunicate with wireless signals, such as wireless local area networks(WLAN), wireless wide area networks (WWAN), and wireless personal areanetworks (WPAN). In the example embodiment, WNIC 26 supportscommunication with peripheral devices, such as peripheral display 32,horizontally-disposed touchscreen display 34 and a physical keyboard 36.For instance, information handling system 10 presents visual informationat an integrated display 28 of lid portion 14 using an internal graphicslink to a graphics controller of chipset 22 and presents visualinformation at horizontally-disposed display 34 through a wirelessinterface supported by WNIC 26. In alternative embodiments, variouscombinations of cabled and wireless interfaces with input and outputdevices may be used.

The example embodiment of FIG. 1 depicts horizontally-disposedtouchscreen display 34 placed on a desktop and communicating withinformation handling system 10 to accept end user inputs and presentvisual information. For instance, a virtual keyboard 38 presented ondisplay 34 accepts touches as key inputs and communicates the touchesthrough WNIC 26 to embedded controller 24 so that key inputs areavailable to an operating system or application executing on CPU 18. Asanother example, two totems 40 are placed on display 34 so that an enduser may communicate touch inputs through totems 40 and display 34 oruse by CPU 18. Totems 40 may be implemented in a number of differentmanners to interact with display 34 and information handling system 10.In one example embodiment, totems 40 are dumb devices that communicatethrough display 34 only by touches; in alternative embodiments, totems40 may integrate processing and wireless communication resources thatsupplement and enhance interactions with information handling system 10.Display 34 presents a user interface related to totems 40 so that theend user manipulates totems 40 for inputs at the user interface.Examples of user interfaces may include a dial interface that acceptsuser rotation of totem 40 as input values measured relative to apresented dial, or a bar interface that accepts sliding motion of totem40 as input values measure relative to a presented bar. Generally, totem40 may provide end user inputs with a variety of usage models, such asby mimicking a mouse or joystick, or interacting in a specific mannerwith defined applications.

Totems 40 provide a convenient and inexpensive interface device thatflexibly adapts to different types of displayed user interfaces,however, accurately detecting and managing totems 40 on touchscreendisplay 34 can present challenges. Typically end users expect minimallatency for recognition and acceptance of inputs at input devices. Totemdevices may provide unique touch signatures on a touchscreen forrecognition of the type of totem, however, latency between detection oftouches and recognition of a totem device input can result in falsemarking of inputs at a display near the totem. For instance,touchscreens typically optimize recognition of finger touches based upona touch area and shape. If a totem 40 only partially touches atouchscreen, the partial touches may not be correctly discerned as partof a totem 40 and instead be interpreted as a finger touch. Where atotem 40 is moved in an uneven manner, such as with partial lifting ofsome portions of totem 40 of touchscreen display 34, incorrectinterpretation of totem touches across the display surface can result inunintended markings and inputs to information handling system 10. Thetotem 40 environment often is further complicated as an end user hand orfingers engaged with totem 40 incidentally touches touchscreen display34 resulting in additional detected inputs. In an active end userengagement, available processing resources may become inundated withrandom and unintentional inputs that overwhelm processing and memorycapabilities, leaving end users with an uncertain and confusedinterface.

Referring now to FIG. 2, a block diagram depicts a system forinterfacing totems 40 on a touchscreen display 34 with a hostinformation handling system 10. In the example embodiment, a host CPU 18accepts end user inputs from an embedded controller 24 based upon imagespresented at a touchscreen display 34 by an operating system 54supporting a touch driver 56. For example, operating system 54 generatesa user interface at pixels 42 of display 34 so that touch driver 56associates detected touches with input values of the user interface. Theuser interface is passed through a graphics processor and to a timingcontroller 46 and/or scalar 48 for presentation as pixel values atpixels 42 of display 34. Touchscreen display 34 includes a protectivetouch surface 44 that integrates capacitive elements to detect touches.For instance, a reference signal passes through capacitive elements ofsurface 44 and is disrupted to varying degrees based upon the proximityand capacitance of objects near surface 44. The electrical signal passesto a touch controller 50, which determines touch events and passes thetouch events to embedded controller 24. For example, finger touches aredetermined at X and Y (length and width) coordinates of display 34related to the pixel 42 locations that presented a user interface.Operating system 54 then applies the inputs to the user interface todiscern end user input values, such as for an application running overoperating system 54.

In the example embodiment, totems 40 resting on protective touch surface44 generate touch inputs across an area of display 34 that exceeds thearea typically associated with finger touches. Conventional touchscreensoften filter out large touch areas under the assumption that the touchesrepresent an unintended input, such as a palm or hand instead of thefinger touches generally associated with end user inputs. However,totems 40 offer an input interface to touchscreen display 34 thatenhances an end user interaction by mimicking a variety of conventionalinput devices, such as dials and bars adapted to allow hand grasps andmovements instead of just finger touches. In order to provideidentification of totems 40 and resolution of inputs at totem 40 withminimal latency, totem contact points 58 are placed on a bottom surfaceof a totem 40 to provide multiple touch contacts within a totem toucharea. Touch controller 50 receives signals for protective touch surface44 based upon the capacitance of the totem contact points 58 andprovides the signals to a totem analyzer 52 for resolution of a totemlocation in length and width at the display 34 and the rotationalorientation of the totem relative to the length and width axes. Touchcontroller 50 then forwards a single location resolution to theoperating system as a length, width and rotational orientation set ofvalues for the whole totem touch area. By performing totem touchanalysis with totem analyzer 52 using a dedicated processing resourceand embedded code, rapid and accurate totem input values are provided tooperating system 54 with minimal latency and reduced consumption of hostprocessing resources.

Totem analyzer 52 is, for example, a digital signal processor (DSP)tuned to perform spectral analysis on signals input from protectivetouch surface 44 to touch controller 50. Rather than attempting topinpoint and identify multiple touch areas associated with a particulartotem, totem analyzer 52 applies spectrum analysis to the touchcontroller signals so that a totem pattern is detected across the time,frequency and/or phase domains. In the example embodiment, uniquefrequency domain signatures are created by multiple parallel touchcontact points 58 placed along a totem bottom surface. Spectrum analysisby totem analyzer 52 associates a detected signature with a totem typeand applies the signature to determine length, width and rotationalorientation of the totem 40. Totem analyzer 52 may maintain a library offrequency domain signatures and totem identifiers, or may generate alibrary by creating totem signatures in a totem configuration routine.For example, an end user places a totem on touch surface 44 an initiatesa configuration routine so that totem analyzer 52 captures the totemsignature from touch controller 52 in the frequency domain. A uniquesignature is provided by placing specific geometric patterns of totemcontact points 58 on the bottom surface of totem 40. For example,parallel pairs of touchpoints in particular provide readily identifiablesignatures responsive to spectral analysis for fast and accuratetracking to totem location rotational orientation. After a spectralanalysis signature is found for totem location, the totem configurationroutine traces movements and rotations of the totem 40 across display 34to associate detected signatures by totem analyzer 52 with definedmotions. The totem 40 location and rotational orientation are reportedto operating system 54 as length, width and rotational orientationresolved from spectrum analysis instead of as a plurality of individualcontact points that would consume operating system 54 and CPU 18resources to resolve.

As another improvement that provides rapid and accurate totem tracking,touch controller 50 enforces ignore zones 60 proximate to totems 40 sothat touch surface 44 regions associated with unintended consequencesare filtered from touch analysis. For example, ignore zones 60 aredefined at locations likely to receive inadvertent finger or palmtouches and automatically enforced based upon detection of a totem. Thearea and relative location of ignore zones may vary based upon the usagemode detected at touch surface 44. For example, ignore zones 60 aredeployed to match likely areas of inadvertent touches for a given userinterface projected next to totem 40, such as based upon end userfinger, thumb and palm positions relative to totem 40. In one exampleembodiment, ignore zones 60 may vary based upon an image of touchsurface 44 captured by a camera of an information handling system 10 sothat the proximity of a user to the totem and the user's intentionsimpact the size and location of ignore zones 60. In another exampleembodiment, hysteresis of different lengths are applied for touches inan ignore zone 60. For example, if an end user hand has weight or iscaptured in an image as placed over totem 40, a longer hysteresis periodis applied to touches in ignore zone 60 than if the end user has afinger extended to make inputs at touch surface 44.

Referring now to FIG. 3, a flow diagram depicts a process for defininghost information handling system interactions with totems 40 disposed ona touchscreen display 44. The process starts at step 62 with detectionof object patterns such as plural foot on a touchscreen 40. In oneexample embodiment, foot detection is performed with a DSP performingspectral analysis on raw signals provided for touchscreen display 44 tocapture patterns of capacitive touches in a frequency domain matchingknown totem types. For instance, placement of plural pairs of feettouchpoints on a bottom surface of totem 40 generates a unique signatureas signals sweep over time through touchscreen 40. In alternativeembodiments, the touch locations themselves may be individual measuredfor location on touchscreen 40 and compared against expected locationsfor known totem types. At step 64, the object identification schemes areassociated with totem type to establish a tracking profile of the totem.At step 66, the objects are analyzed for orientation relative totouchscreen 44 to establish a rotational orientation of the totem 40 asan initial starting point. During initial detection of a totem 40, othertypes of inputs may be applied to provide a more rapid and accuratedetermination of totem 40 identification, such as images captured by acamera of the totem and totem location.

At step 68, totem 40 position is reported to a host operating system asa length, width and rotational orientation on touchscreen 44. Spectralanalysis or similar dedicated processing focused on totem identificationand tracking provides a simplified position reporting of totem inputsfor the host operating system to handle. For example, each totemidentifier includes a single defined central location and rotationalorientation based upon relative location of feet or other contact zonesdisposed at a bottom surface. Totem analyzer 52 applies detectedtouchpoints to resolve the totem position to the central location androtational orientation as a length, width and rotational orientationrelative to the touchscreen display 44. The host operating systemreceives the length, width and rotational position information to applyas inputs, and can resolve specific touch points of the totem as neededfrom the length, width and rotational orientation information. In thismanner, the host operating system avoids expending processing resourceson resolving totem inputs, which can include complex and rapid positionmovements. At step 70, once the totem position is resolved, ignore zonesare defined relative to the resolved totem position. Ignore zones may belocally determined at totem analyzer 52 or may be communicated from thehost operating system to totem analyzer 52. In one alternativeembodiment, touch controller 50 continues to process all touches attouchscreen display 44 and provide all touches to the host operatingsystem; however, the host operating system ignores touches that aredefined as under or proximate to a totem based upon a totem length,width and rotational orientation. By continuing to provide raw touchdata, touch controller 50 offers the host operating system an activeinterface of touch inputs if needed. For instance, the host operatingsystem may perform a periodic retrieval of raw data to define a moreaccurate totem signature, and then update the signature used by totemanalyzer 52 based upon the analysis. As another example, the hostoperating system may completely ignore touches defined as located belowthe totem but monitor touches in other ignore zones to discernunintended from intended inputs. Once ignore zones are defined at step70, the process continues to step 72 to define a hysteresis for thetotem position and configuration, as is explained in greater depthbelow. At step 74 totem touches are processed according to the definedignore zones and hysteresis so that at step 76 changes in position arereported at step 68 to the host operating system. Resolution of changesin totem position is determined at totem analyzer 52 for reporting tothe host operating system in length, width and rotational positionformat.

Referring now to FIG. 4, an example embodiment depicts a system fortracking interaction settings of totems disposed on a touchscreendisplay. Tracking multiple totem touchpoints as a group under a singletotem identifier improves processing efficiency and reduces inputlatency, however, the gross position reporting to the host operatingsystem also simplifies processing of additional touches. As an example,manipulation of a totem can result in temporary lifting of touchpointsof the totem in an irregular pattern that may alter a display userinterface as the totem presence is detected and then disappears. Thetemporary removal of some totem touchpoints from a touchscreen display44 followed by full placement of totem touchpoints can introduceadditional latency as totem presence is de-registered and re-registeredwith each movement. As another example, partial placement of a totem ofthe touch surface may result in presentation of inadvertent andunintended touches as the totem recognition is effected and removed.Bifurcation of totem touch analysis between a dedicated totem analyzerand a host operating system reduces latency and incorrect intermediatetouch readings by allowing host or dedicated processing of totemdetection with hysteresis based upon totem configuration and position.

In order to improve totem location processing, touch controller 50maintains a totem table 78 that tracks detected totems based upon atotem identifier. Touch controller 50 stores the location of the totemfor a hysteresis time period so that temporary touchpoint lift off andtouchscreen noise do not create inaccurate inputs. In one embodiment,touch controller 50 implements the hysteresis by storing inputs in atotem location for a hysteresis period of time whenever detected touchestransition from those matching a totem to other types of touches. Ifbefore expiration of the hysteresis time period the totem is againdetected at the location, then a temporary liftoff of one or more totemtouch points is assumed and the intermediate touches are discarded. Incontrast, if the hysteresis time period expires without detection of thetotem at the totem location, the intermediate touches are applied asintended touches and forward to the host operating system. In analternative embodiment, hysteresis is managed at the host operatingsystem by immediately forwarding touches not identified with a totem tothe operating system to process. For example, a liftoff of one or moretouchpoints of a totem results in totem analyzer 54 removing the groupof touches as associated with a totem so that individual touches of theremaining totem touch points are forwarded to the host operating system;however, the host operating system applies the hysteresis beforeprocessing the touches as individual inputs instead of totem touches. Invarious embodiments, responsibility for determining the association of agroup of touches to a totem versus to individual touches is allocatedbetween various hardware and software components in the chipset, CPU,embedded controller, touch controller, BIOS and operating system toprovide balance between responsiveness to touch inputs and consumptionof processing resources. For example, forwarding touch inputs to thehost operating system during hysteresis time periods allowspreprocessing of the inputs in the event a totem is not subsequentlydetected.

Totem table 78 of FIG. 4 provides a number of configuration options fortotem identifiers to enforce ignore zones and hysteresis based upon acontext at the user interface. In the example embodiment, a dial userinterface 80 accepts inputs from totem 40 by a rotational movement oftotem 40. Totem 40 has an ID of “1” that defines a spectral signature,ignore zones and hysteresis based upon a probable usage model. Since thedial user interface is associate with rotation of totem 40, ignore zonesdefined proximate totem 40 relate to probable use of totem 40, such as afinger ignore zone 84 along the upper perimeter of totem 40, a palmignore zone 86 along at the lower side of totem 40, and a thumb ignorezone 88 at a corner periphery location. A second totem 40 has an ID of“2” that defines a spectral signature used with a bar user interfaceconfiguration 82 that moves the totem 40 across a length or width oftouchscreen display 44. A finger ignore zone 84 has a length thatprovides for movement of fingers in association with lateral movement ofthe totem 40, and the palm ignore zone 86 has a similar length toaddress anticipated sliding of the palm has a totem 40 is movedlaterally. Touch controller 50 adapts inputs proximate totems 40 to usespectral signatures, ignore zones and hysteresis that dynamicallyconfigure to usage models appropriate for the context, such as byadjusting hysteresis to have a shorter time period where small totemmovements are expected and a longer time period where larger movementsare expected and have an increased likelihood of lifting totem touchpoints off of a touchscreen.

Referring now to FIG. 5, a flow diagram depicts a process for adaptingtotem input responsiveness based upon totem usage states. The processstarts at step 88 with detection of touches at a touch screen. At step90, the touch is buffered for totem hysteresis so that some time passesbefore the touch is applied as an input. At step 92 a determination ismade of whether the detected touches are associated with a totem, suchas if a spectral analysis of the touches matches a stored totem spectralsignature. If a totem is not detected at step 92, the process continuesto step 94 to present the touch at the touchscreen display or otherwiseprocess the touch as an input. At step 96, subsequent touches arebuffered for the totem hysteresis to continue to monitor touches forassociation with a totem device. At step 98, after a sufficient numberof touches are compared with the totem signature without detecting atotem, the process ends at step 100 to accept the touches as normaltouch inputs. If at step 98 a touch is associated with a totem afterhysteresis has passed, the process continues to step 102 to undo thetouch presentation or input.

If at step 92 a totem is detected, the process continues to step 104 toreport the totem position. Totem position is reported as a singlelocation of length, width and rotational orientation relative to thetouchscreen display dimensions. The single location relates to a knowntotem footprint so that the host operating system can determine actualtotem coverage of the touchscreen display from the single location. Inthis manner, the host operating system presents user interfaces relatedto the totem, such as the dial and bar user interfaces, at the peripheryof the totem footprint. At step 106, the totem position is tracked as atouch zone that reports the single position to the host operatingsystem, such as a length, width and rotational orientation position. Thetotem is tracked as a gross touch area by reference to the spectralsignature of the totem on the display rather than by reportingindividual touch points of the totem to the host operating system. Atstep 108, motion of the totem is detected with an alteration in theposition of the totem touch zone. At step 110, the touch position of thetotem is buffered for a hysteresis time period to reduce the risk ofinaccurate readings introduced by noise or that a removal of the totemhas occurred. If at step 112 the totem is still indicated at thetouchscreen display, the process returns to step 106 to track the newtotem position. If the totem has been removed or is otherwise nottracked as an appropriate signature, the process returns to step 92 toanalyze the touch.

As is depicted by FIG. 5, totem hysteresis adapts to different timeperiods based upon a number of different factors, including the type oftotem, the user interface configuration relative to the totem, therelative position of the totem to the touchscreen display and theanticipated end user interactions. For instance, before placement of thetotem on the touchscreen display, a hysteresis is applied for a firsttime period to all touchscreen detected touches. Once a totem isdetected, a different hysteresis time is applied for movementsassociated with the totem than for other touches. For example, detectionof a spectral signature associated with a totem can provide an increasedaccuracy for totem location that reduces the need for extendedhysteresis to filter inadvertent movements. As another example, anincreased hysteresis time may apply if a totem signature is lost at atouchscreen display since an increased chance for inadvertent ornoise-type touches increases during placement and removal of a totem.Application of independent hysteresis periods is simplified wherededicated spectral analysis processing to identify and track totemsprovides single location identification and reporting for a totem.

Referring now to FIG. 6, a flow diagram depicts a process for adjustingtotem responsiveness based upon totem motion. Responsiveness is adaptedby adjusting both the ignore zones and the hysteresis assigned to atotem based upon context. As an example, defining a broader ignore zoneand ignoring totem motion until the motion breaches an ignore zoneboundary provides greater assurance that a movement of the totem isintended. If a bar type user interface is involved, varying the size ofthe ignore zone based upon expected movements in essence adaptshysteresis of the totem to the direction of movement of the totem. Forexample, a greater movement of a totem is required to breach an ignorezone in a direction of movement that is not expected while a smallerignore zone is breached more quickly in a direction of movement that isexpected. A combination of varying ignore zone sizes and varyinghysteresis time periods based upon touchscreen context provides adaptivebehavior for totems independent of other touch input detections. Asanother example, a context for establishing totem ignore zones andhysteresis is the proximity of a totem to a boundary of a touchscreendisplay so that inaccuracies related to movement of the totem off thetouchscreen display are better managed.

At step 114, a totem is detected, such as with spectral analysissearching for totem signatures based upon unique dispositions ofparallel touchpoint feet pairs on a totem bottom surface. At step 116,ignore zones and hysteresis are defined for the totem based upon thetotem context. At step 116, detection of motion of the totem isperformed with analysis of touches or other indicia, such as cameraimages of the touchscreen display surface, user hand positions detectedon the touchscreen, weight placed upon the totem or Bluetooth signalssuch as may be sent in response to detection of accelerations at thetotem by an integrated accelerometer. Upon detection of motion, theprocess continues to step 120 to define ignore zones and hysteresisbased upon the change in context introduced by the motion. For example,if an intended end user movement is confirmed by multiple indicia, amore responsive totem input may be configured with reduced ignore zonesize and hysteresis. In contrast, if other indicia point to anunintentional input, such confirmation that the end user hand is awayfrom the totem, then a larger ignore zone and hysteresis may be applied.At step 122 a determination is made of whether motion has completed. Ifnot, the process continues to monitor context at step 120 to adapt totemresponsiveness. If motion is completed, the process returns to step 116to define a stationary context for the ignore zones and hysteresis.

Referring now to FIG. 7, a side cutaway view depicts a totem havingtouch contact points 140 with variable capacitance and havinginteractions with light output at the display. In the exampleembodiment, capacitance of a foot 140 is adjusted based upon a positionof totem 40 by bring a capacitance source 138 selectively into contactwith foot 140 based upon context, such as weight resting on totem 40.For example, hand pressure overcomes an upward bias of a weight switch136 so that capacitance source 138 electrically interfaces with foot140. When a conductive path is opened between capacitance source 138 andfoot 140, the capacitance at the touch pad increases to provide anenhanced touch input signal strength associated with foot 140. The totemanalyzer looks for amplitude associated with the touch foot 140 thatindicates presence of a weight at totem 40 before “activating” totem 40.As set forth above, weight on totem 40 introduces a context thatindicates an increased likelihood of an end user input, so detection ofthe weighted capacitance touch results in setting of ignore zones andhysteresis for a pending end user input based upon the input context,such as the user interface presented at the touchscreen display.

In the example embodiment depicted by FIG. 7, totem 40 includes someintelligence that supports communication with a host informationhandling system in ways other than touches at a touchscreen display. Amicrocontroller 124 executes embedded code that manages a wirelesspersonal area network (WPAN) such as Bluetooth, an accelerometer 128 anda charger system 132 that charges an integrated battery 130. Activecommunication through a wireless interface may provide a basis fortransitioning between different ignore zone and hysteresisconfigurations. Battery 130 provide current to power microcontroller 124and receives charge from charger 132 based upon conversion of lightenergy provided from the touchscreen display with a light sensor/charger142. Other light detectors 134 deployed at different angles andlocations on the bottom surface of totem 40 provide microcontroller 124with indications of light output from the touchscreen display, such asthe color or intensity of light in a particular positions along thebottom surface of totem 40. In this manner, a host operating systemmanages control of totem 40 functions by sending commands to totem 40with light signals presented from beneath totem 40. For example, atouchscreen display presents light at a defined location, color,intensity or flashing on and off so that signals generated by lightdetector 134 and communicated to microcontroller 124 includes commandinformation related to functions of totem 40, such as haptic feedback,charging of battery 130 or definition of a relative rotationalorientation. The host operating system applies the totem locationinformation and totem footprint information to define illumination onlybelow the totem so that the communication and charging functions remainhidden from an end user.

A variety of functions become available with bi-directional totemcommunication supported through illumination of a display detected by alight sensor. One example is registration of totems with a passive andnon-wireless communication. For example, if a host information handlingsystem detects multiple totems on a touchscreen display, the host canconfirm the identity of each totem by illuminating beneath each totem inturn and getting feedback from the totems, such as with a wirelessconfirmation or a haptic response at the totem. As another example, atotem relative orientation may be determined by illumination of thedisplay at specific locations relative to the totem so that lightsensors disposed in different quadrants of the bottom surface of thetotem detect the light and place the totem rotational position. Asanother example, a totem that has a battery requests battery charge witha wireless or haptic indication so that the host operating systemprovides illumination at a bright setting. In one example embodiment,information sent by illumination under a totem provides for automatedBluetooth pairing between the totem and a host information handlingsystem, such as by sending an encryption code with the illumination. Invarious other embodiments, other types of functions may includeimplementation of a rotational encoder that uses light to determinerotational orientation, a button press response to the totem based uponan illumination started from the host, totem status feedback and hapticfeedback triggering in which a haptic response is initiated at the totemfrom illumination under the totem by the host operating system.

Referring now to FIG. 8, a state diagram depicts totem settings basedupon detected weight placed upon the totem. The process starts at step144 with detection of the totem on the touchscreen display. At step 146,a determination is made of whether the detected totem is in a conductivestate or a non-conductive state. For example, a conductive state isestablished when pressure on the upper surface of the totem pressesweight switch 136 to interface a capacitive source 138 with a foot 140.A non-conductive state exists when a foot 140 is detected as a touchhaving a lower capacitive reading at the touchscreen. In one embodiment,rapid recognition of conductive state is provided by recognition of aspectral signature at the touchscreen display having increased amplitudeassociated with greater capacitance of the touching foot and or feet. Ifa step 146 a non-conductive state is detected, the process continues tostep 152 to apply non-touch settings for the ignore zone and hysteresisof the totem. If at step 146 a conductive state is detected at thetotem, the process continues to step 148 to apply touch settings forignore zones and hysteresis of the totem. The precise settings for aparticular non-touch or touch totem will depend upon context of thetotem, such as the expected inputs or usage model associate with thetotem. Although FIG. 8 depicts a passive communication of anticipateduse by a totem through manipulation of capacitive features of the totemfeet, in alternative embodiments, alternative active communication couldbe used.

Referring now to FIG. 9, a block diagram depicts totem 40 interactionsmanaged locally at a touchscreen display 34 scalar 48. Typically display34 settings and management are performed at a host information handlingsystem, such as through a graphics processor managed by an operatingsystem. However, if an operating system is unavailable or communicationhas latency, coordination of inputs made at a display 34 through theoperating system and back to the display controller, such as timingcontroller 46, can introduce latency that detracts from systemresponsiveness. In order improve system responsiveness related to toteminputs, the example embodiment in FIG. 9 relies upon scalar 48 supportof touch inputs related to touchscreen 34 and totem 40 interactions. Forexample, touch controller 50 includes embedded code that maintains acommunication interface with operating system 54 while re-routing totem40 and touchscreen 34 activities to scalar 48. Scalar 48 includes amicrocontroller that parses touch events to selectively map touch eventsto appropriate inputs at touchscreen 34 that are implemented locally.For example, scalar 48 selects totem touch inputs associated withdisplay settings to apply the display settings locally without directionfrom operating system 54. Display settings may include displaybrightness, contrast, menu, function and power settings that generallyapply to the display image across all pixels. In some embodiments,display settings routed to scalar 48 for application locally at display34 are also forwarded to operating system 54 so that specificapplications executing on the information handling system may adjustvisual image output responsive to the display settings. For instance,scalar 48 adjustment of gamma at display 34 based on inputs made at atotem 40 and routed directly to scalar 48 will also have the gammasetting forwarded to the host information handling system so thatapplications running over operating system 54 may adapt their colorgamut to the selected display gamma. In one embodiment, touch controller50 simply forwards all totem related touches to both scalar 48 and hostoperating system 54 so that each can handle touches as appropriate.

FIG. 9 depicts an example embodiment with touchscreen display 34 havingtotems 40 deployed in defined zones that have inputs selectively managedby an operating system 54 or a scalar 48. A first totem 40 rests in anoperating system touch zone 152 so that touches made at the totem 40 areforwarded as position reports to operating system 54. A second totem 40rests on a scalar touch zone 154 so that touches made at the totem 40are instead managed locally by scalar 48. In the example embodiment, adisplay setting user interface 156 is presented proximate the secondtotem to direct end user display setting inputs, such as brightness andcontrast. For example, the display setting user interface may bepresented under the management of operating system 54 or as anintegrated interface of scalar 48 or timing controller 46. Touch zonesare defined in a touch zone table 158 that defines which portions of thetouchscreen are designated to accept operating system versus scalarinputs. A context engine 160 manages the touch zones and the totemsettings based upon the context detected at the touchscreen display. Astouch controller 50 detects touches, the touches are forwarded through aphysical or logical multiplexor so that scalar 48 or operating system 54manages the touches as inputs. For example, touches detected inoperating system touch zone 152 are ignored by scalar 48 and managed byoperating system 54. In contrast, touches detected in scalar touch zone154 are managed by scalar 48 while operating system 48 may or may notselect to receive and address the inputs. For instance, operating system48 may accept touches that were made in scalar touch zone 154 to keeptrack of display settings.

Referring now to FIG. 10, a touchscreen display 34 is depicted havingillumination zones managed to interact with a totem 40. In the exampleembodiment, three example illumination zones are depicted. A chargeillumination zone 164 is established below a totem 40 having a solarcell or similar light-to-current converter that converts displayillumination into a power source for components within a totem 40. Arotational orientation zone 166 has illumination provided in a specificportion of the totem footprint so that light detectors disposed in thetotem will detect stronger light if located closer to the illuminatedportion. A communication illumination zone 168 provides illumination ina predefined illumination color, intensity or timed pattern tocommunicate information to totem 40 from a local display controller,such as scalar 48, or the host operating system 54. In operation, totem40 management at display 34 may be handled by local display control oroperating system control based upon the function involved and thedisplay-to-host connection state.

In one example embodiment, totem 40 communicates a low battery charge todisplay 34 with a Bluetooth command, a haptic vibration, or a change incapacitance at one or more of plural feet. The request for a charge ishandled by operating system 54 if totem 40 is located in an operatingsystem tracking zone 152 and is handled by scalar 48 if totem 40 islocated in scalar touch zone 154. If display 34 does not have an activeinterface with a host operating system, scalar 48 manages all totemcommunications. Upon receipt of the request for charge of the lowbattery, display 34 illuminates charge illumination zone 164 to provideillumination that charges the battery. Charge illumination zone 164 maybe sized and located based upon the central location reported for thetotem and the stored footprint of the totem 40. Alternatively, chargeillumination zone 164 is located based upon analysis of individualtouches at display 34 that define the boundary of totem 40. In oneembodiment, charge illumination zone 164 is reduced in size if ambientlight conditions are low, such as where light escaping from underneathtotem 40 may disrupt an end user working environment having a darkenedroom.

In another example embodiment, totem 40 responds to communications fromscalar 48 or host operating system 54 sent with illumination below totem40. For instance, if a host operating system 54 desires to know therelative rotational orientation of totem 40, illumination in arotational orientation zone 166 provides illumination at a rotationalorientation that results in current generation at a light sensor locatednear the illumination. Totem 40 provides the relative location of theillumination with a Bluetooth, haptic or capacitive feedback. Similarly,if scalar 48 or host operating system 54 desires to command a responseat a totem 40, such as a haptic response, communication illuminationzone 168 is established below the totem 40 to send illumination thatincludes the command. For example, display 34 illuminates commands withones and zeroes by sequencing illumination in a timed pattern. Asanother example, plural communication illumination signals may beprovide below a totem 40 to help establish a more reliable signal, suchas by using one communication illumination zone as a timing signal whilesending ones and zeroes through the other communication illuminationzone.

Referring now to FIG. 11, a flow diagram depicts a process forcommunicating with a totem using illumination at the totem bottomsurface. The process starts at step 170 with detection of the totem onthe touchscreen display. The totem location may reflect resolution ofthe totem analyzer using spectrum analysis and application of storedtotem footprint specifications or independent confirmation of the totemposition with analysis by a host operating system of independent touchinformation provided from the touch controller. For example, calibrationof totem footprint specifications may be performed by the operatingsystem with comparison of expected and detected touches by the touchcontroller proximate the ignore zones. At step 172, display 34illuminates under the totem position with a predefined color, intensityor timed light pattern. Initial illumination may calibrate the lightintensity for the totem that the totem will receive from the display 34as inputs. For example, many displays 34 will have a maximum intensitylevel available that will produce a different current response at thetotem. Initial illumination provides a baseline for input illuminationlevels that adapt the totem to different displays and also allow aparticular display to use a lower illumination if desired. At step 174,light sensors at the totem bottom surface convert detected light tocurrent that is in turn provided to a microprocessor operating on thetotem. At step 176, the totem microprocessor applies detectedillumination to execute functions associated with commands communicatedby the detected illumination. As set forth above, some examples ofcommands include establishing encrypted Bluetooth communication bysending a key, initiating a haptic feedback at the totem by powering avibration device integrated in the totem, establishing a relativerotational orientation of the totem and initiating charge byillumination provided to a totem solar cell exposed at the totem bottomsurface. At step 178, where appropriate totem 40 responds to theillumination command by performing the function or by acknowledging thecommand with a response that indicates the command was received anexecuted.

Referring now to FIG. 12, a flow diagram depicts a process forcoordinating charge of a totem battery with touchscreen displayillumination. The process starts at step 180 with detection of a lowbattery charge state at the totem. At step 182 a battery lownotification is communicated to the touchscreen, such as with aBluetooth, haptic or capacitive feedback. At step 184, the notificationis detected by the host operating system, such as by receiving aBluetooth message or a capacitive input through the touch controllerthat is initiated by a capacitive foot capacitance change or hapticinput. At step 186, the low battery charge information is forwarded tothe touchscreen display scalar so that at step 188 the scalar presentsillumination in the charge illumination zone for establishing currentfrom the totem solar cell to the battery charger.

Referring now to FIG. 13, a block diagram depicts a system for detectinga totem spectral signature. In various embodiments, touches at a touchsurface are detected with various types of analog signal analysis.Generally an object proximate the touch screen alters mutual couplingbetween row and column electrodes or an absolute capacitance increasescapacitance to ground. A sequential scan of the electrode positionsdetects touches based upon differences in capacitance over time. When atotem is placed upon a touch sensor surface, an area of the size andshape of the totem generates capacitance detectable by a touchcontroller, however the processing involved in comparing a touch area toan expected totem footprint based upon touch positions can lead tolatency in totem detection, especially if the totem identification isperformed at a host operating system level. Sufficient processing powerand memory capacity is required to digitize touch points from analogsensors within the touchscreen, filter these points appropriately,swiftly identify single finger touch points, swiftly identify simplelarge objects such as circles, identify and reject palm/forearm/largeobject irregular shapes, identify potential large object regular shapesfor spectral analysis. Spectral analysis of the digitized signals iscompute intensive, however, a dedicated digital signal processor handlesthe computations rapidly to send a resolved totem position that removesprocessing workload from the host operating system. The same algorithmsused within the touch controller to spectrally identify totems can alsobe run within the host system processing the digitized object data thatrepresents unknown objects on the touchscreen, relying on the hostsystem to reject the object or identify the object as a unique totem. Atotem outline is normalized and then extrapolated to complete apseudo-frequency table that reflects an outline of a binary object as acomplete single period amplitude sweep. A frequency windowing expansionis executed in order to allow appropriate mathematical extents thatidentify a totem spectral signature. The frequency window results in arepeatable output set of points with amplitude per frequency based upontotem contact regions. A pure single sine wave results in a singlefrequency output so that an object matching a single sine wave creates asingle frequency with no side band components Matching a spectralsignature to a totem permits rapid position reports based upon length,width and rotational orientation that effectively filters the totemtouches from processing by the algorithms running either on the embeddedtouch controller or the host operating system.

In the example embodiment, touch sensor 190 includes a touch controller50 that detects touch positions on a touch device, such as a touchscreendisplay or capacitive mat. The touch position analog signal is monitoredby a touch module 192 that reports capacitive values related to touchesbased upon the detected touch positions. A spectral module 194 alsomonitors the touch position analog signal for spectral signaturesassociated with a totem position. For example, spectral module 194monitors an analog signal sweep across the touchscreen display for afrequency, phase and amplitude associated with totem touch areas. Touchmodule 192 and spectral module 194 report detected touches to a touchUSB stack 196 for communication from touch sensor 190 to a host system.

A peripheral display embedded controller USB stack 198 receives fromtouch sensor 190 the touch detection of touch module 192 and thespectral signature of spectral module 194. Detected touches areforwarded to an human interface device (HID) detection handler 200 forresolution by the host system. Spectral signatures are forwarded to aspectral signature filter 202 for analysis to compare with possibletotem spectral signatures. Totem analyzer 52 reports totem matches tospectral signature filter 202, such as with a resolution of totem typeand position based upon the detected spectral signature. A touch outputmodule 204 combines the touch and totem detection to output to hostinformation handling system 10 resolved positions for use at anapplication layer. In one embodiment, totem spectral signatures areapplied to filter out touches provided by HID touch detection module 200that fall within a totem spectral signature area. Alternatively,individual touches provided by HID touch detection module 200 arecompared with totem spectral signature areas to confirm the detectedtotem.

Referring now to FIG. 14, an example embodiment depicts a totem positionresolved from spectral analysis. In the example embodiment, a totemtouch region 206 extends along a totem bottom surface in an oblong shapethat resolves in an embedded touch controller layer 210 to a length,width and rotational orientation position. A host detection layer 212has a dead zone 208 defined by relation to the totem position 206 toreduce host touch processing. Although depicted as a single touchregion, totem touch region 206 may include individual touch positionswithin the defined totem area that further identify the totem. In analternative embodiment, unique totem touch locations may be resolved onan individual basis to determine a totem, such as a prearranged patternof touch points (parallel lines, circle-shaped, or star-shaped touchpoints). Once the host operating system resolves the touch points as atotem position, the totem position is provided to totem analyzer 52 sothat totem analyzer can associate the detected spectral analysissignature with the totem identification provided from the host operatingsystem. In another alternative embodiment, initial identification of atotem is provided by touch controller detection of totem touch regionsand then tracking of the totem position is performed with the spectralsignature associated with the totem identification reported by the hostoperating system.

Referring now to FIG. 15, an example embodiment depicts a totem positionresolved from spectral analysis of multiple totem touch regions 206. Inthe example embodiment, three totem contact regions 206 providesufficient spectral signature to track totem position and estimate afourth totem touch region lifted from the touch screen. For example,totem analyzer 52 may include spectral signatures for incomplete totemtouch regions to support spectral signature totem tracking where a totemis not completely placed on the touch surface. Once a totemidentification is resolved based upon the spectral signature, a deadzone 208 is defined for the projected totem footprint to allow the hostoperating system to reduce its workload by ignoring touches in thetouchscreen region associated with the totem.

Referring now to FIG. 16, an example embodiment depicts a totem positionresolved from spectral analysis of a circular totem touch region. As setforth above, the totem identification may be performed by comparison ofthe frequency domain signal from the touchscreen or by comparison ofdetected touch areas with known totem footprints. Once the totemidentification is resolved, position and rotational orientation aretracked by changes detected in the spectral signature. A dead zone 208defined relative to the predicted totem position removes workload fromthe host operating system for tracking inputs at the touchscreen.

Although the present invention has been described in detail, it shouldbe understood that various changes, substitutions and alterations can bemade hereto without departing from the spirit and scope of the inventionas defined by the appended claims.

What is claimed is:
 1. An information handling system comprising: aprocessor operable to execute instructions to process information; amemory interfaced with the processor, the memory operable to store theinformation; a display interfaced with the processor and memory, thedisplay operable to present the information as visual images, thedisplay having touchscreen operable to detect touch inputs made at thedisplay; a touch controller interfaced with the touchscreen and theprocessor, the touch controller operable to analyze touches detected atthe touchscreen and to provide inputs determined from the analyzing tothe processor; a totem resting on the touchscreen, the totem havingplural contact regions at a bottom surface, the touch controllerdifferentiating the totem from other touches based upon the spatialrelationship of the plural contact regions with each other; and a totemanalyzer associated with the touch controller, the totem analyzercommunicating totem position to a processor as length, width androtation values, the totem analyzer enforcing a predetermined hysteresisfor touches at the touchscreen proximate the totem.
 2. The informationhandling system of claim 1 wherein the totem analyzer comprises adigital signal processor having spectral analysis engine tuned to detectthe totem contact regions.
 3. The information handling system of claim 1wherein the predetermined hysteresis comprises a first time valueenforced if a non-totem touch is detected by the touch controller withina predetermined distance of the totem and a second time value if onlytotem touches are detected by the touch controller within thepredetermined distance.
 4. The information handling system of claim 3further comprising a hysteresis buffer storing timestamped touch inputsdetected by the touch controller, the totem analyzer removing touchespresented at the touchscreen display and stored in the hysteresis bufferby associating the touches with incomplete placement of a totem on thetouchscreen display.
 5. The information handling system of claim 4wherein the totem analyzer applies hysteresis buffer corrections over afirst time period with a first level of motion detected at thetouchscreen display and over a second time period with a second level ofmotion detected at the touchscreen display.
 6. The information handlingsystem of claim 5 wherein in motion is determined from analysis imagescaptured by a camera proximate to the touchscreen display.
 7. Theportable information handling system of claim 1 wherein the totemcontact regions comprise plural feet extending from the totem bottomsurface.
 8. The portable information handling system of claim 7 whereinthe predetermined hysteresis comprises withholding presentation ofnon-totem touches proximate a totem position for at least apredetermined time if less than all totem contact regions are detectedat the touchscreen display.
 9. A method for interfacing an informationhandling system with a totem device, the method comprising: detectingplural contact regions of the totem on a touchscreen display surface;identifying the totem from a geometric pattern defined by the pluralcontact regions; detecting motion associated with one or more of theplural contact regions; and in response to the detecting motion,applying a predetermined hysteresis to detected touch inputs, thehysteresis delaying communication of touches proximate a totem positionto a processor of the information handling system if less than all ofthe totem plural contact regions are detected on the touchscreen displaysurface.
 10. The method of claim 9 further comprising: determining aresting state associated with the one or more of the plural contactregions; and in response to determining a resting state, applying apredetermined resting hysteresis to detected touch inputs proximate thetotem position.
 11. The method of claim 9 further comprising:determining a distance of a touch to a detected totem contact region;and adapting the predetermined hysteresis to at least a first or secondtime period based at least in part on the distance.
 12. The method ofclaim 9 further comprising: buffering timestamped touch inputs detectedat the touchscreen; and removing buffered touches presented at thetouchscreen display by associating the touches with incomplete placementof a totem on the touchscreen display.
 13. The method of claim 9 whereindetecting motion associated with one or more of the plural contactregions further comprises capturing an image of an end user handproximate the totem.
 14. The method of claim 9 further comprising: inresponse to detecting motion, defining an ignore zone proximate thetotem; and ignoring touch inputs detected at the touchscreen displaybased at least in part on the ignore zones.
 15. An information handlingsystem input device comprising: a touchscreen display having a touchcontroller that detects touch positions at the touchscreen display; atotem having plural contact regions resting on the touchscreen display,the touch controller detecting the plural contact regions; a totemanalyzer associated with the touch controller, the totem analyzercommunicating totem position to a processor as length, width androtation values based upon a spectral signature of the plural contactregions, the totem analyzer enforcing a predetermined hysteresis fortouches at the touchscreen proximate the totem.
 16. The informationhandling system input device of claim 15 wherein the totem analyzerenforces one or more ignore zone extending out from a periphery of thetotem by a predetermined distance based upon one or more predeterminedfactors.
 17. The information handling system input device of claim 15wherein the predetermined hysteresis comprises a first time valueenforced if a non-totem touch is detected by the touch controller withina predetermined distance of the totem and a second time value if onlytotem touches are detected by the touch controller within thepredetermined distance.
 18. The information handling system of claim 15further comprising a hysteresis buffer storing timestamped touch inputsdetected by the touch controller, the totem analyzer removing touchespresented at the touchscreen display and stored in the hysteresis bufferby associating the touches with incomplete placement of a totem on thetouchscreen display.
 19. The information handling system of claim 15wherein the predetermined hysteresis depends at least in part upon theavailability of camera images captured of the totem.
 20. The informationhandling system of claim 15 wherein the totem contact regions compriseplural feet extending from the totem bottom surface.